This is the preview version of the Wisconsin State Legislature site.
Please see http://docs.legis.wisconsin.gov for the production version.
NR 153.17(4)(c) (c) A list of the best management practices for which funding is requested, including property acquisition associated with any of these practices, and identification of practice eligibility under s. NR 153.15. For land acquisition, a certification statement that the applicant will obtain control of the property upon which the practice will be constructed prior to commencement of the grant period.
NR 153.17(4)(d) (d) A list of local assistance and design activities for which funding is requested and an identification of eligibility under s. NR 153.16.
NR 153.17 Note Note: Local assistance activities eligible for reimbursement are identified in s. NR 153.16. Reimbursement may also be sought for design and construction services work under s. NR 153.15 (1) (a).
NR 153.17(4)(e) (e) Certification that the activities listed on the application are scheduled for completion within the allowable time period specified by the department in the application materials.
NR 153.17(4)(f) (f) Certification that the applicant has made arrangements to provide the staff necessary to implement the project.
NR 153.17(4)(g) (g) Certification that staff and contractors designated for the project have adequate training, knowledge, and experience to implement the proposed project.
NR 153.17(4)(h) (h) Evidence that the proposed project does not conflict with statewide and targeted nonpoint source performance standards and prohibitions.
NR 153.17(4)(i) (i) For agricultural projects, documentation that the county has a qualifying strategy to implement state agricultural performance standards and prohibitions contained in subch. II of ch. NR 151. To qualify, the strategy shall address the following key actions:
NR 153.17(4)(i)1. 1. Inform and educate landowners and land operators required to comply with performance standards.
NR 153.17(4)(i)2. 2. Conduct compliance status inventories based on records reviews and on-site visits.
NR 153.17(4)(i)3. 3. Document inventory results and maintain compliance status records.
NR 153.17(4)(i)4. 4. Report inventory results and continuing compliance maintenance requirements to landowners and operators.
NR 153.17(4)(i)5. 5. Identify best management practices to achieve compliance.
NR 153.17(4)(i)6. 6. Apply for grants from the department, or work to secure grants from other state, federal, or local sources to provide cost sharing to landowners and land operators to achieve compliance with performance standards.
NR 153.17(4)(i)7. 7. Develop cost-share agreements and provide for technical assistance to landowners and land operators to achieve compliance with performance standards.
NR 153.17(4)(i)8. 8. Assist the department at its request in drafting ch. NR 151 notices to landowners and land operators.
NR 153.17(4)(i)9. 9. Fulfill annual program reporting requirements.
NR 153.17(4)(j) (j) Other information that the department may require to screen the application for compliance with minimum program and statutory requirements.
NR 153.17(5) (5)Required scoring information for large scale projects. An applicant for any large-scale TMDL project or large-scale non-TMDL project shall submit the following information to be considered for funding under this chapter:
NR 153.17(5)(a) (a) Receiving water quality need, including impairment or threats to water quality caused or contributed to by nonpoint pollution sources that will be addressed by the project.
NR 153.17(5)(b) (b) Expected reduction in pollutant loading attributed to the project.
NR 153.17(5)(c) (c) Potential for the desired water quality response to implementation of best management practices.
NR 153.17(5)(d) (d) Justification for geographic extent of the proposed project area.
NR 153.17(5)(e) (e) Information regarding specific nonpoint pollution sources in the project area and the need and strategy for collecting and evaluating additional inventory information.
NR 153.17(5)(f) (f) Proposed nonpoint pollution control strategy for the project area, including contacting and educating landowners and operators, conducting farm evaluations, identifying and targeting high priority nonpoint pollution sources such as sites failing to meet state standards and prohibitions, selecting cost-effective best management practices, delivering cost sharing and technical assistance, using local and state regulatory tools to facilitate attainment, and continuing maintenance of state performance standards and prohibitions.
NR 153.17(5)(g) (g) Evidence of local support and involvement including support from governmental units, interest groups, landowners, and land operators. The department may also request information concerning a governmental unit's continuous decision-making process which ensures participation by minority and low income populations in affected areas, along with majority populations, to ensure that as an outcome all people receive the benefits of a clean, healthy, and sustainable environment regardless of race, national origin, or income.
NR 153.17(5)(h) (h) Consistency of the proposed project with other local land and water resource management plans, including the county land and water resources management plan.
NR 153.17(5)(i) (i) Project budget and cost-effectiveness.
NR 153.17(5)(j) (j) Partnerships in the project area, including the extent to which available federal funding and other staffing and financial resources will be used.
NR 153.17(5)(k) (k) Strategy for evaluating changes in pollution potential, pollutant loading, and receiving water response after implementation of the project.
NR 153.17(5)(L) (L) The extent of local authority to enforce performance standards and prohibitions, including information required to determine the project score enforcement multiplier under s. NR 153.19 (4).
NR 153.17(5)(m) (m) For the city of Racine, an explanation of how the proposed project will contribute to meeting storm water requirements under ch. NR 216.
NR 153.17(6) (6)Required scoring information for small scale projects. An applicant for any small-scale TMDL project or small scale non-TMDL project shall submit the following information to be considered for funding:
NR 153.17(6)(a) (a) Receiving water quality need, including impairment or threats to water quality caused or contributed to by nonpoint pollution sources that will be addressed by the project.
NR 153.17(6)(b) (b) Expected reduction in pollutant loading or pollution potential attributed to the project.
NR 153.17(6)(c) (c) Extent to which performance standards and prohibitions will be implemented.
NR 153.17(6)(d) (d) Potential for the desired water quality response to implementation of best management practices.
NR 153.17(6)(e) (e) Evidence of local support and involvement, including support from governmental units, interest groups, landowners, and land operators. The department may also request information concerning a governmental unit's continuous decision-making process which ensures participation by minority and low income populations in affected areas, along with majority populations, to ensure that as an outcome all people receive the benefits of a clean, healthy, and sustainable environment regardless of race, national origin, or income.
NR 153.17(6)(f) (f) Consistency between the project and other state and local resource management plans.
NR 153.17(6)(g) (g) Project budget and cost effectiveness.
NR 153.17(6)(h) (h) Use of other funding sources to supplement or reduce the state cost share provided under this chapter.
NR 153.17(6)(i) (i) Strategy for evaluating changes in pollution potential, pollutant loading, and receiving water response after implementation of the project.
NR 153.17(6)(j) (j) Extent of local authority to enforce performance standards and prohibitions, including information required to determine the project score enforcement multiplier under s. NR 153.19 (4).
NR 153.17(6)(k) (k) For the city of Racine, an explanation of how the proposed project will contribute to meeting storm water requirements under ch. NR 216.
NR 153.17 History History: CR 00-025: cr. Register September 2002 No. 561, eff. 10-1-02; CR 09-112: r. and recr. Register December 2010 No. 660, eff. 1-1-11; correction of numbering of (3), (4) made under s. 13.92 (4) (b) 1., Stats., Register December 2010 No. 660.
NR 153.18 NR 153.18Targeted runoff management project screening. This section applies only to targeted runoff management projects.
NR 153.18(1) (1) The department may deny consideration of applications that are incomplete by the submittal deadline. The department may consider an application incomplete if the project proposal requires significant additional review to determine compliance with other state laws and the department determines that such reviews may significantly delay the project. State laws that the department may consider in determining if the application is incomplete include those to protect navigable waters, wetlands, historic places, historic properties, endangered resources, or threatened resources and laws for managing environmental hazards due to site contamination.
NR 153.18(2) (2) The department shall screen each completed project application to determine if the project meets basic eligibility criteria for funding under this chapter. The department shall use the information required in s. NR 153.17 (4) to make this determination. The department shall remove from further consideration applications that fail to satisfy screening requirements and shall inform the applicant of this decision.
NR 153.18 History History: CR 00-025: cr. Register September 2002 No. 561, eff. 10-1-02; CR 09-112: am. Register December 2010 No. 660, eff. 1-1-11.
NR 153.19 NR 153.19Targeted runoff management project scoring.
NR 153.19(1)(1)Applicability. This section applies only to targeted runoff management projects.
NR 153.19(2) (2)Scoring procedure for small scale projects. The department shall use the procedure in this subsection to score any small scale project that passes the eligibility screening under s. NR 153.18.
NR 153.19(2)(a) (a) The department shall develop an initial project score using the information submitted by the applicant under s. NR 153.17 (6).
NR 153.19(2)(a)1. 1. The department shall assign a sub-score to each of the application elements identified under s. NR 153.17 (6). The initial project score shall be the sum of the sub-scores.
NR 153.19(2)(a)2. 2. In determining the initial project score for small scale projects, the department shall give greatest weight to water quality need, extent of pollution control, and cost-effectiveness.
NR 153.19(2)(a)3. 3. The department may establish minimum score requirements to identify projects that should be removed from further consideration.
NR 153.19(2)(b) (b) The department shall multiply the initial project score by a factor based on local enforcement authority to determine the final project score. The department shall determine the local enforcement factor in accordance with sub. (4).
NR 153.19(3) (3)Scoring procedure for large scale projects. The department shall use the procedure in this subsection to score any large scale project that passes the eligibility screening under s. NR 153.18.
NR 153.19(3)(a) (a) The department shall develop an initial project score using the information submitted by the applicant under s. NR 153.17 (5).
NR 153.19(3)(b) (b) The department shall multiply the initial project score by a factor based on local enforcement authority to determine the final project score. The department shall determine the local enforcement factor in accordance with sub. (4).
NR 153.19(4) (4)Multipliers for local enforcement authority.
NR 153.19(4)(a)(a) The department shall increase the initial project score in accordance with this subsection if there are local regulations adopted prior to application submittal that give local authority to enforce state performance standards and prohibitions. The result shall be the final project score.
NR 153.19(4)(b) (b) The department shall increase the initial project score in accordance with the following for projects that are agricultural in nature.
NR 153.19(4)(b)1. 1. The department shall multiply the initial project score by a factor of 1.15 if the applicant certifies to the department that it has local authority to enforce all state agricultural performance standards and prohibitions at all sites within the local jurisdiction where such state agricultural performance standards and prohibitions apply.
NR 153.19(4)(b)2. 2. The department shall adjust the enforcement multiplier based on the scope of the local ordinance coverage. Adjustments under this subdivision shall be made so that the multiplier is greater than 1.0 but less than 1.15 for instances where the local regulations cover some, but not all, of the state agricultural performance standards and prohibitions or where a local regulation is applicable to some, but not all, of the sites where the state agricultural performance standard or prohibition applies. The department may request that a copy of applicable ordinances be made available to the department for review in determining the enforcement multiplier.
NR 153.19(4)(b)3. 3. The department may adjust the multiplier if the ordinance contains a variance clause that significantly reduces the effectiveness of the ordinance in achieving compliance with the state agricultural performance standards or prohibitions, or both.
NR 153.19(4)(b)4. 4. If no multiplier is earned, the initial score shall be the final project score.
NR 153.19(4)(c) (c) The department shall increase the initial project score in accordance with the following for projects that are urban in nature:
NR 153.19(4)(c)1. 1. The department shall multiply the initial project score by a factor of 1.15 if the applicant certifies to the department that it has local authority to enforce all state non-agricultural performance standards and prohibitions at all sites within the local jurisdiction where such state non-agricultural performance standards and prohibitions apply.
NR 153.19(4)(c)2. 2. The department shall adjust the enforcement multiplier based on the scope of the local ordinance coverage. Adjustments under this subdivision shall be made so that the multiplier is greater than 1.0 but less than 1.15 for instances where the local regulations cover some, but not all, of the state non-agricultural performance standards and prohibitions or where a local regulation is applicable to some, but not all, of the sites where the state non-agricultural performance standard or prohibition applies. The department may request that a copy of applicable ordinances be made available to the department for review in determining the enforcement multiplier.
NR 153.19(4)(c)3. 3. The department may adjust the multiplier if the ordinance contains a variance clause that significantly reduces the effectiveness of the ordinance in achieving compliance with performance standards.
NR 153.19(4)(c)4. 4. If no multiplier is earned, the initial score shall be the final project score.
NR 153.19(4)(d) (d) If the department is required to assign a multiplier pursuant to this section and the project is not clearly rural or urban in nature, the department, in consultation with the applicant, shall choose and apply one of the multipliers in accordance with par. (b) or (c).
NR 153.19 History History: CR 00-025: cr. Register September 2002 No. 561, eff. 10-1-02; CR 09-112: r. and recr. Register December 2010 No. 660, eff. 1-1-11.
NR 153.20 NR 153.20Targeted runoff management project selection and funding.
NR 153.20(1) (1)Applicability. This section applies only to targeted runoff management projects.
NR 153.20(2) (2)Selection.
NR 153.20(2)(a)(a) The department shall assign each project application to one of the four project categories identified in s. NR 153.14 (2).
NR 153.20(2)(b) (b) From the total budget available to fund targeted runoff management projects, the department shall create annual budget sub-allocations for each of the project categories the department intends to fund in the application cycle. Sub-allocations may change from year to year. The amount in each sub-allocation shall be based on the department's water quality goals and the quality of applications submitted.
NR 153.20(2)(c) (c) Projects compete for funding only against other projects in the same category.
NR 153.20(2)(d) (d) Within each category, the department shall place the projects on a statewide selection list.
NR 153.20(2)(d)1. 1. For each small scale project category, the department shall use the following procedure to create the statewide selection lists:
NR 153.20(2)(d)1.a. a. Identify the highest scoring project in each department region. Provided that the highest regional project score is equal to or greater than the median score for all qualifying applications submitted statewide, place the project with the highest regional score at the top of the statewide selection list. If the highest scoring project in the department region is less than the median for all qualifying applications, the project may not be moved to the top of the statewide selection list and shall be ranked with other projects in accordance with subd. 1. b.
NR 153.20 Note Note: This will increase the likelihood that at least one project from each department region will be at the top of the statewide selection lists for each small scale project category.
NR 153.20(2)(d)1.b. b. Following projects with the highest regional score, the department shall place all remaining eligible projects on the statewide selection list, in rank order from highest to lowest score.
NR 153.20(2)(d)1.c. c. Projects shall be selected in order from the top to the bottom of the statewide selection lists until available funds have been allocated.
NR 153.20(2)(d)2. 2. For each large scale project category, the department shall use the following procedure to create the statewide selection lists:
NR 153.20(2)(d)2.a. a. The department shall place all eligible projects on the statewide selection list, in rank order from highest to lowest score. There may be no regional adjustments in the ranking for large-scale projects.
NR 153.20(2)(d)2.b. b. Projects shall be selected in order from the top to the bottom of the statewide selection lists until available funds have been allocated.
Loading...
Loading...
Published under s. 35.93, Stats. Updated on the first day of each month. Entire code is always current. The Register date on each page is the date the chapter was last published.